EaserixDocs
DevelopersAPI referenceSignNotary

Self-serve listing

Create a listing for a notary not in the seeded registry. Goes to pending_claim until an operator verifies it against the state commission record. One profile per account (409 otherwise).

View as Markdown
POST
/v1/notary/profiles

Authorization

bearer
AuthorizationBearer <token>

In: header

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Response Body

application/json

application/json

application/json

application/json

curl -X POST "https://example.com/v1/notary/profiles" \  -H "Content-Type: application/json" \  -d '{    "fullName": "string",    "state": "string",    "commissionNumber": "string"  }'
{  "profile": {    "id": "string",    "slug": "string",    "status": "string",    "fullName": "string",    "state": "string",    "stateName": "string",    "commissionNumber": "string",    "commissionExpiresAt": "2019-08-24T14:15:22Z",    "onlineAuthorized": true,    "city": "string",    "county": "string",    "languages": [      "string"    ],    "specialties": [      "string"    ],    "bio": "string",    "availabilityNote": "string",    "accepting": true,    "sessionsCount": 0,    "active": true,    "claimedAt": "2019-08-24T14:15:22Z",    "created": "2019-08-24T14:15:22Z"  },  "message": "string"}

Update my profile

Self-editable fields only. Registry facts (name, state, commission) change through claim verification or registry sync, never here.

Claim an unclaimed listing

Authenticated claim of a registry-seeded listing. The commission number must match the registry record (403 otherwise), and the claim stays pending until an operator verifies it — impersonation is the attack this flow exists to beat.