> Production API availability: use /api/v1/help?view=guides and the resource operations catalog before following a recipe. Some localhost capabilities are not deployed yet; an absent operation is unavailable.
What this module owns
Structured resume profiles with guarded edits to experience and project entries.
Patch an existing entry
GET /api/v1/resumes/{objectid} returns updated_at, data_sha256 and data. PATCH requires expected_updated_at and patches. Match an experience by company plus role, or a project by name.
{
"expected_updated_at": "COPY_FROM_THE_CURRENT_GET",
"patches": [{
"section": "projects",
"match": { "name": "COPY_AN_EXISTING_PROJECT_NAME" },
"set": { "summary": "Revised factual summary." }
}]
}A patch must match exactly one entry. Unsupported fields and invalid value types are rejected. A project URL must use HTTPS. PUT replaces the data and additionally requires expected_data_sha256. Stale revisions return 409. The handler also uses updateDataIfUnchanged at the write boundary. Run the resume contract and entry-patch tests before changing this contract; sync the associated Databoard after source changes.
First read
Use API_URL with /api/v1, for example http://localhost/api/v1. Set API_KEY privately. Replace any resource placeholder with an ID returned by discovery.
curl --fail-with-body "$API_URL/resumes" \
-H "Authorization: Bearer $API_KEY"Registered agent routes
The entries below are extracted from the current route and handler source. Scope tokens can represent alternatives or different method branches, not a requirement to grant every listed scope. Body fields are observed inputs, not a complete required-field schema. Follow the resource guide and the deployed validation response for a write.
/api/v1/resumes
Intended request methods: GET. Confirm allowed_methods and method_evidence in the deployed operations catalog; documented methods do not grant access.
Scope tokens in the implementation: resume:read
Selected rejection messages:
- Use GET
/api/v1/resumes/{objectid}
Intended request methods: GET, PATCH, PUT. Confirm allowed_methods and method_evidence in the deployed operations catalog; documented methods do not grant access.
Scope tokens in the implementation: resume:read, resume:write
Observed JSON fields: data, expected_data_sha256, expected_updated_at, patches.
Selected rejection messages:
- Use GET, PATCH, or PUT
- Resume not found
- Patch is too large
- expected_updated_at is required
- Resume changed; fetch it again before patching
- expected_data_sha256 and data are required
- Resume data changed; fetch it again before replacing
Access boundary
External agents use only the versioned operations documented above and returned by the deployed catalog. Browser actions and internal controllers are not substitutes for missing API operations.
Verification before automation
Read back the owned record after a write. On a dedicated local fixture, test missing input, wrong owner, missing scope and stale revisions where supported. Confirm the request did not change state when rejected. Check the generated projection separately from the source record. Never replay sends, payments or deletion requests merely to test connectivity.
See API validation and remaining gaps for the shared test strategy.
HTTP discovery and safety contract
Read GET /api/v1/help?view=guide&resource=resumes for this module's machine-readable guidance. Discover supported operations through its discovery_url when present. A null discovery_url means no direct resource API is documented; related endpoints, when provided, have their own ownership and scope requirements.
Use GET /api/v1/me with your key to confirm identity and scopes. Only request methods and fields supported by this deployment. The shared transport boundary rejects unsupported methods and malformed JSON on covered routes, but field schemas and revision checks remain resource-specific. Notes and Carousels expose typed save schemas and payload-only validation; other modules must not be assumed to share that contract.
Create, update, replace, patch, delete, send and publish are distinct capabilities. An operation absent from the returned catalog is unavailable, not permission to guess a URL. Read back after writes; after a timeout inspect the result before retrying. Never automatically replay a payment, message, deployment or deletion.