Register an agent for a sandbox key
Changed onSelf-serve agent onboarding: no account, no request body, no human step. Returns a sandbox API key (oxi_sk_test_...) and the path to live access. The key works only on the sandbox server (https://0xinsider.com/sandbox/api/v1), where it is optional: send it as Authorization: Bearer to exercise the credential path, and the sandbox answers a malformed key with the production 401. Nothing is stored, so the key cannot be listed or revoked and does not expire; register again for a new one. The live API answers a sandbox key with 401 invalid_api_key and error.reason sandbox_api_key. Live data needs an account with an active Pro subscription, and either an oxi_sk_live_ key from https://0xinsider.com/developers or an OAuth access token (https://0xinsider.com/auth.md). The request body is not read.
Request
- Base URLhttps://api.0xinsider.com
- Authnone required
Headers
Opt into strict query-name validation. The default is compatible: unknown names are ignored and reported in X-Query-Ignored. With strict, an unknown name returns 400 bad_request with error.reason unknown_query_parameter before the handler runs, including when its percent escape is incomplete.
Response
A new sandbox key. Every call returns a different key, with Cache-Control: private, no-store.
Changes
- warning
added the new
freshness_ceiling_unsatisfiedenum value to the/response property for the response status - warning
added the new
freshness_ceiling_unsatisfiedenum value to the/response property for the response status - warning
added the new
freshness_ceiling_unsatisfiedenum value to the/response property for the response status
3 more changes in this revision
- warning