How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Tines Credentials API

Manage stored credentials for integrations

Tines Credentials API is one of 7 APIs that Tines publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Credentials. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, and rate-limit docs.

This API exposes 5 operations across 2 paths, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 2 base URLs: https://{tenantDomain}/api/v1, https://{tenantDomain}/api/v2.

5 operations 2 paths 4 schemas 1 DELETE2 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://{tenant-domain}/api/v1
Authentication
HTTP Bearer, API Key
Resource Areas
1

Authentication & Security 2

Tines Credentials API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (BearerAuth). An API key is passed in the header as X-User-Token (ApiKeyAuth). By default, every request must be authenticated.

  • BearerAuth — Bearer token authentication using an Tines API key. Format: Authorization: Bearer
  • ApiKeyAuth — API key authentication using the X-User-Token header. Format: X-User-Token:

Paths & Operations 5

Across 2 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Credentials 5

Manage stored credentials for integrations

GET
/user_credentials
List credentials
listCredentials 3 params → 200401404422
POST
/user_credentials
Create a credential
createCredential body → 200401404422
GET
/user_credentials/{id}
Get a credential
getCredential 1 param → 200401404422
PUT
/user_credentials/{id}
Update a credential
updateCredential 1 param body → 200401404422
DELETE
/user_credentials/{id}
Delete a credential
deleteCredential 1 param → 200401404422

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are CredentialCreate (17 properties), Credential (16 properties), Error (1 property), PaginatedMeta (1 property). Each schema is shown below with its type and property counts.

PaginatedMeta
object
1 property
Credential
object
16 properties
Error
object
1 property
CredentialCreate
object
17 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tines-credentials-api-openapi.yml Raw ↑

Other APIs Tines publishes across the network.

Tines Actions API
Tines Audit Logs API
Tines Folders API
Tines Stories API
Tines Tags API
Tines Teams API
Where this information came from

This is an independent, third-party profile of Tines Credentials 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.