Glossary
Bearer token
A bearer token proves who is calling and is sent in the Authorization header. OneLifeVibe ingest calls need the world's own ingest key as one.
Updated November 12, 2026
- Standard
- RFC 6750
- Also called
Authorization: Bearer
At OneLifeVibe
- POST /api/platform/v1/ingest without the world's own ingest key as a bearer token. Client keys (olvp_…) never work for ingest.
Related terms
What it means
A bearer token is a credential you put in the Authorization header. The word bearer describes the rule: whoever holds the token is treated as the caller. RFC 6750 defines this pattern for HTTP requests. The token itself is the proof, so you do not add another credential for the same call.
Related terms include access token audience (aud), API key, and OAuth protected resource metadata. Audience tells a resource server which API a token is meant for. Protected resource metadata is how a service can publish the authorization details for a protected resource. A bearer token is the header format; an API key or an access token is the value you put in it.
How it works
Send the request with a header named Authorization. The value is the word Bearer, a space, and the token. In examples this looks like Authorization: Bearer followed by the token value. Do not put the token in the URL or the body when the API expects this header.
The server reads the header and checks the token. If the token is missing or invalid, the call fails. HTTP APIs commonly answer with 401 for a missing or invalid token and 403 when the token is valid but not allowed to do the action. The exact code comes from the API you call.
How OneLifeVibe uses it
OneLifeVibe uses bearer tokens for ingest. To call POST /api/platform/v1/ingest, send the world's own ingest key as a bearer token in the Authorization header. Client keys (olvp_…) never work for ingest. The ingest key is the credential for that endpoint, and a client key is not a substitute.
Keep the key types separate in your code. The ingest key belongs to a world, so use the key for the world you are calling. If you have an olvp_ key in the header for POST /api/platform/v1/ingest, replace it with the world's own ingest key. Do not assume that a client key proves anything for ingest, because OneLifeVibe does not accept it there.
Common mistakes
Leaving out the Authorization header is a common mistake, and so is dropping the word Bearer. Some clients put the token in a query string because it is easy to test that way. The bearer pattern uses the header, and RFC 6750 defines that shape.
The OneLifeVibe mistake to avoid is using a client key for ingest. Client keys (olvp_…) never work for POST /api/platform/v1/ingest. Use the world's own ingest key as the bearer token instead.
Another mistake is using an ingest key from a different world. The key is the world's own key, so match it to the world you are calling. If a request fails, check the header format and the key source before you change your payload.
Questions
Where does a bearer token go in an HTTP request?
It goes in the Authorization header as Authorization: Bearer followed by the token value. RFC 6750 defines this format. The token is the proof of the caller, so you do not add a second proof to the same request.
How do I authenticate POST /api/platform/v1/ingest on OneLifeVibe?
Send the world's own ingest key as a bearer token in the Authorization header. Client keys that start with olvp_ never work for ingest. Use the ingest key for the world you are calling.
See it working. The OneLifeVibe connector and Platform API put these pieces together.
Written from the OneLifeVibe tool registry and platform configuration, and checked automatically before publishing. Something wrong? Tell us.