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

Searchcraft Authentication API

The Authentication API from Searchcraft — 2 operation(s) for authentication.

Searchcraft Authentication API is one of 10 APIs that Searchcraft 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 and API documentation.

This API exposes 6 operations across 2 paths, and defines 1 schema. It is described by OpenAPI 3.0.1, at version 1.0.

Requests are made against a single base URL, https://your-cluster.searchcraft.io.

6 operations 2 paths 1 schemas 2 DELETE2 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
1.0
Base URL
https://your-cluster.searchcraft.io
Authentication
API Key
Terms of Service
Resource Areas
1

Authentication & Security 1

Searchcraft Authentication API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (SearchcraftKey). By default, every request must be authenticated.

  • SearchcraftKey — Searchcraft access key passed directly in the Authorization header (no "Bearer" prefix). Keys are tiered by permission: read (search), ingest (document, synony…

Paths & Operations 6

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

Authentication 6
GET
/auth/key
Lists all access keys on the cluster.
listKeys → 200
POST
/auth/key
Creates a new access key with the given permissions.
createKey body → 200
DELETE
/auth/key
Deletes all access keys on the cluster.
deleteAllKeys → 200
GET
/auth/key/{key}
Retrieves the details of a specific access key.
getKey 1 param → 200
POST
/auth/key/{key}
Updates a specific access key.
updateKey 1 param body → 200
DELETE
/auth/key/{key}
Deletes a specific access key.
deleteKey 1 param → 200

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is AccessKey (5 properties). Each schema is shown below with its type and property counts.

AccessKey
object
An access key definition. The permission field is a bitmask where read is 1, ingest is 15, and admin is 63; keys may be scoped to indexes and associated with o…
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

searchcraft-authentication-api-openapi.yml Raw ↑

Other APIs Searchcraft publishes across the network.

Searchcraft Documents API
Searchcraft Federation API
Searchcraft Healthcheck API
Searchcraft Indexes API
Searchcraft Measure API
Searchcraft Search API
Searchcraft Stopwords API
Searchcraft Synonyms API
Searchcraft Transactions API
Where this information came from

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