You can also manually add keys to Tyk using your own key-generation algorithm. It is recommended if using this approach to ensure that the OrgID being used in the API Definition and the key data is blank so that Tyk does not try to prepend or manage the key in any way.
The Tyk Dashboard API Access Credentials
ID of API the keys grant access to. Can either be the internal or external API ID.
The Key ID.
If you are not sure if a key is hashed you can send this as true.
true, false Use the hash of the key as input instead of the full key. Any none empty string will be interpreted as to say you want to use hash input.
Set to true if the passed key ID is a username.
true, false Adding the suppress_reset parameter and setting it to 1, will cause Tyk not to reset the quota limit that is in the current live quota manager. By default Tyk will reset the quota in the live quota manager (initialising it) when adding a key. Adding the suppress_reset flag to the URL parameters will avoid this behaviour.
1000
[
"641c15dd0fffb800010197bf",
"615d2e528bf3980001c7c6c2"
]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
1710302205
20000
-1
1715681745
1000
0
["edge", "edge-eu"]10
-1