Outbrain Authentications API
TokenObtaining a token should be your 1st step toward using Amplify API. You need to include it in all further requests using the HTTP Header OB-TOKEN-V1.In order to protect your privacy, the tokens are valid for a period of 30 days. You will not be able to access Amplify API using an expired token.You can generate as many tokens as you wish. Generating a new token does not invalidate older tokens.When a user password or email are changed in the Create Token Page all tokensgenerated prior to the change are revoked and a new token must be generated.How to obtain a token ?There are 2 ways to obtain a tokenvia web interfaceSimply go to your Amplify API Token Page, fill in your password, hit generate, and you will get your token.If you can't see Amplify API Token form, this means that your username doesn't have access to the Amplify API. To register for the Amplify API please fil
Outbrain Authentications API is one of 23 APIs that Outbrain publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Authentications. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, API documentation, and a support channel.
This API exposes 1 operation across 1 path, and defines 1 schema. It is described by OpenAPI 3.2.0, at version 0.1.
Requests are made against a single base URL, https://api.outbrain.com/amplify/v0.1.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
Outbrain Authentications API declares
2 security schemes
for authenticating requests.
An API key is passed in the header as OB-TOKEN-V1 (OBTokenAuth).
It accepts HTTP basic authentication (BasicAuth).
By default, every request must be authenticated.
OBTokenAuth— Token obtained from GET /login (HTTP Basic) or from https://my.outbrain.com/create-token. Valid for 30 days.BasicAuth— HTTP Basic credentials used only on GET /login to obtain an OB-TOKEN-V1 token.
Paths & Operations 1
Across 1 path, the API surfaces 1 operation — 1 GET. Each is listed below with its method, path, parameters, and response codes.
Token Obtaining a token should be your 1st step toward using Amplify API. You need to include it in all further requests using the HTTP Header OB-TOKEN-V1. In order to protect you…
Schemas 1
The contract defines 1 schema that model the data the API accepts and returns. The most detailed is Error (2 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Outbrain 12
Other APIs Outbrain publishes across the network.
This is an independent, third-party profile of Outbrain Authentications API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.