Reference / API

API Reference

The Mark API provides programmatic access to verification, identity lookup, and signing request management. All endpoints require an API key.

Base URL

https://api.mark.noblestar.tech/api/

All requests must include the X-Api-Key header.

Authentication

Every request requires an API key passed in the X-Api-Key header. API keys are scoped to a project and can be created in the Mark dashboard.

curl -H "X-Api-Key: your-api-key" https://api.mark.noblestar.tech/api/verify/ABC123

POST /verify

Verify a signed bundle or verification code.

Parameter

Type

Description

code

string

Verification code (6-character alphanumeric)

bundle

object

Raw SignedBundle JSON (alternative to code)

document_hash

string

Optional — verify the bundle matches this document hash

Response: Returns the verification result with pass/fail for each of the five checks (signature validity, key authorization, temporal validity, revocation status, on-chain anchor).

GET /identities/:fingerprint

Look up an identity by its key fingerprint. Returns the current service record, trust tier, and active subkeys.

Signing requests

Method

Path

Description

POST

/signing-requests

Create a new signing request (co-signing envelope)

GET

/signing-requests/:id

Get signing request status and signatures

POST

/signing-requests/:id/sign

Add a signature to a signing request

Rate limits

API requests are rate-limited per API key:

Verification — 100 requests/minute
Identity lookup — 60 requests/minute
Signing requests — 30 requests/minute

Rate limit headers (X-RateLimit-Remaining, X-RateLimit-Reset) are included in every response.

Error handling

Status

Meaning

400

Invalid request body or parameters

401

Missing or invalid API key

404

Resource not found (expired code, unknown identity)

429

Rate limit exceeded

500

Internal server error

All error responses include a JSON body with code and message fields.

Next:MSP Specification›