Create a key.
Tyk will generate the access token based on the OrgID specified in the API Definition and a random UUID. This ensures that keys can be owned by different API owners should segmentation be needed at an organisational level.
API keys that have no access_rights data after Tyk Gateway applies their Policies are master keys. A master key can access all APIs on the system. Tyk Gateway creates master keys only if allow_master_keys is set to true. Always set access_rights data on a key, or apply a Policy, to limit the key to the APIs that it needs.
Authorizations
The Tyk Dashboard API Access Credentials
Query Parameters
Set this to true to create a basic user. Note you have to send basic_auth_data(user and password) in the request body if this value is set to true.
Body
"portal-developer@example.org"
1000
deprecated use apply_policies going forward instead to send a list of policies ids
"641c15dd0fffb800010197bf"
0
"2024-05-14T13:15:46.560506+03:00"
true
1716895221
false
0
0
"1715681746"
5
"5e9d9544a1dcd60001d0ed20"
60
Defines the action to take on a Session in Redis after it expires. Valid values are "retain" and "delete", leave empty for legacy session lifetime controls.
retain, delete "delete"
Duration in seconds to retain a Session in Redis after it expires. Used with post_expiry_action "retain". Set to -1 to retain indefinitely. Set to 0 to use legacy session lifetime controls.
0
1710302205
20000
-1
1715681745
1000
0
10
-1