Addresses API · events
Replay committed registry events at-or-after since
GET /events
Replay committed registry events at-or-after since (a journal sequence number), oldest first: every address the registry learned — buildings and units — with its canonical form, coordinates and the source that verified it.
The registry is the platform's, so its facts are the platform organization's: any other organization replays an empty journal. One response is a page: limit defaults to 500 and is capped at 5000 (an over-cap request is clamped). Pages are sequence-ordered and the boundary is stable — repeat with since=<last event's sequence + 1> until a page comes back smaller than limit to replay the journal exactly once. upTo (inclusive) ends the replay at a sequence instead of the journal's head — with GET /events/head it replays the journal as it stood at a moment. Appends nothing: a read of facts already journalled.
Access
Requires activity:read.
How scopes come from roles: Scopes and roles. Getting a token: Authentication and app tokens.
AI agent tool
No agent tool. The journal replay a consumer pages through to build its projection; agents read the projections the list and get tools serve, and the audit trail (audit_trail) for history.
Connecting an agent: AI agents.
Example
curl -X GET 'https://addresses.getmanifold.io/events?since=1&limit=500' \
-H "Authorization: Bearer $MANIFOLD_TOKEN"const response = await fetch("https://addresses.getmanifold.io/events?since=1&limit=500", {
method: "GET",
headers: { Authorization: `Bearer ${process.env.MANIFOLD_TOKEN}` },
});
if (!response.ok) throw new Error(`${response.status}: ${await response.text()}`);
const answer = await response.json();[
{
"_tag": "addresses.address-registered",
"eventId": "evt_01a1c0de-2a00-7b10-8c20-3d4e5f6a7b80",
"txId": "tx_01a1c0de-2a00-7b10-8c20-3d4e5f6a7b81",
"tenantId": "org_00000000-0000-0000-0000-000000000000",
"sequence": 1,
"occurredAt": "2026-10-29T02:10:00.000Z",
"source": "address-manager",
"version": 1,
"actor": {
"_tag": "system",
"id": "address-manager:registry"
},
"correlationId": "tx_01a1c0de-2a00-7b10-8c20-3d4e5f6a7b81",
"payload": {
"address": {
"id": "pad_0b3f6c1e-4a7d-8e29-9c51-7f2d4e8a6b10",
"countryCode": "AU",
"streetNumber": "200",
"streetName": "COLLINS",
"streetType": "ST",
"locality": "MELBOURNE",
"region": "VIC",
"postcode": "3000",
"street": "200 Collins Street",
"lines": [
"200 Collins Street",
"Melbourne VIC 3000"
],
"geocode": {
"latitude": -37.8152,
"longitude": 144.9671,
"precision": "rooftop"
},
"verification": "platform-verified",
"confidence": {
"score": 0.9,
"level": "verified"
}
},
"key": "AU|200|COLLINS|ST|MELBOURNE|VIC|3000|",
"evidence": [
{
"source": "provider",
"name": "fake",
"matched": "address",
"checkedAt": "2026-10-29T02:10:00.000Z"
}
]
}
}
]The panel writes this call in other languages. It does not send it: Manifold's APIs do not take calls from a web
page on another site, so run the call from your own code or terminal. The whole API as OpenAPI: address-manager.openapi.json. Base URL https://addresses.getmanifold.io.
Errors
Every refusal is a status and a JSON body whose _tag names it. A refused call changes nothing.
401
| Refusal | What it means | What to do |
|---|---|---|
Unauthorized reason | The token is missing, expired or not one Manifold issued. | Get a fresh token and send the call again. |
TokenAlreadyUsed tokenId | A single-use app token was already spent. | Mint a new token for this call. |
402
| Refusal | What it means | What to do |
|---|---|---|
SubscriptionRequired status | The organization's subscription has lapsed, so writes are refused. | An owner settles billing. Reads still work meanwhile. |
403
| Refusal | What it means | What to do |
|---|---|---|
TenantRequired userId | The token names no organization. | Choose the organization, then get a new token. |
ScopeRequired required | The token's roles do not grant the scope this call needs. | Ask an owner or admin for a role that grants it. |
409
| Refusal | What it means | What to do |
|---|---|---|
MirroredFromSource source | This area is fed by your source system until the organization goes live. | Make the change in the source system, or go live first. |
503
| Refusal | What it means | What to do |
|---|---|---|
RequestLogUnavailable tokenId, reason | The service could not record the request, so it did nothing. | Try again shortly. |
How refusals work everywhere: Errors.