Vic.ai Authentication API
To initiate the authentication process, send a POST request to `/v0/token` withthe payload as shown in the example below:```json{ "client_id": "VIC_CLIENT_ID", "client_secret": "VIC_CLIENT_SECRET"}```Here is an example of how to do this:```bashcurl -X POST https://api.us.vic.ai/v0/token \ -H "Content-Type: application/json" \ -d '{"client_id": "VIC_CLIENT_ID", "client_secret": "VIC_CLIENT_SECRET"}'```Upon providing a valid client ID and client secret, you should receive aresponse similar to the following:```json{ "access_token": "YOUR_ACCESS_TOKEN", "token_type": "Bearer", "expires_in": 3600}```**Token Storage:** If you are storing the `access_token`, ensure your storagemechanism does not impose a character limit. Access tokens use JWT format andmay be 530 characters or longer.For subsequent calls, use the value in `access_token` in the `Authorization`field.Here is an example:```bashcurl https://api.us.vic.ai/v0/healthCheck \ -H "Content-Type: application/json" \ -H "Authorization: Bearer YOUR_ACCESS_TOKEN"```The response should resemble the following:```bash{"company":"Your Company Name","status":"PASS","version":"0.19.0"}```
Vic.ai Authentication API is one of 33 APIs that Vic.ai publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Authentication. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.
This API exposes 1 operation across 1 path, and defines 4 schemas. It is described by OpenAPI 3.1.0, at version v10.40.4.
Requests are made against 3 base URLs: https://api.no.stage.vic.ai, https://api.us.vic.ai, https://api.no.vic.ai.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Vic.ai Authentication API declares
1 security scheme
for authenticating requests.
It accepts HTTP bearer tokens (BearerAuth).
By default, every request must be authenticated.
Paths & Operations 1
Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.
To initiate the authentication process, send a POST request to /v0/token with the payload as shown in the example below: json { "clientid": "VICCLIENTID", "clientsecret": "VICCLIE…
Schemas 4
The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are GetTokenResult (3 properties), Error (2 properties), GetTokenInput (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 Vic.ai 12
Other APIs Vic.ai publishes across the network.
This is an independent, third-party profile of Vic.ai Authentication 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.