Indexing a Moment
This page documents the API endpoint for manually indexing or re-indexing an existing Moment on the In Process protocol. While the protocol includes an automatic indexer, developers can use this endpoint to ensure that any Moment that was missed—or whose onchain metadata has changed—is up-to-date in the In Process database.
Tip: If you want to create a brand-new Moment, see the Create a Moment docs instead.
Endpoint
POST https://inprocess.fun/api/moment/index
Request Body
Send a JSON object with the following fields:
{
"address": "string", // Moment contract address
"tokenId": 1, // (optional) Token ID to index (default: 1)
"chainId": 8453 // (optional) Chain ID (default: 8453 for Base)
}
Body Parameters
Name | Type | Required | Default | Description |
---|---|---|---|---|
address | string | Yes | — | The contract address of the Moment to index |
tokenId | number | No | 1 | The token ID of the Moment to index |
chainId | number | No | 8453 | Chain ID where the contract lives |
Example Requests
cURL
curl -X POST https://inprocess.fun/api/moment/index \
-H "Content-Type: application/json" \
-d '{
"address": "0x06a701Ae65582B92Af48cDff45a8B20DcA3714cA",
"tokenId": 1,
"chainId": 8453
}'
Example Success Response
{
"status": "success",
"message": "Moment indexed",
"moment": {
"address": "0x06a701Ae65582B92Af48cDff45a8B20DcA3714cA",
"tokenId": 1,
"chainId": 8453,
"id": "bceddfb3-28f2-49f3-8669-73a813a06b90",
"uri": "ar://1wMmKuaz-VdxmruOQJuYS-3nfU3zlNKmPNpc79Ou-qM",
"admin": "0x29b6674c1562e31EdFd9709D9576e8E5F1e68d01",
"createdAt": "2025-06-07T20:41:35+00:00",
"hidden": false
}
}
Example Error Response
If the contract or token cannot be found (or another error occurs) the API returns:
{
"status": "error",
"message": "...error message..."
}