Register
A Farmers administrator registers your application. Save the one-time API token securely on your server.
Secure, versioned access to public Farmers content, with signed events for trusted partner servers. A practical foundation for commerce, marketing and professional integrations.
Public APIs are currently read-only. Request an admin-issued key; never place the key in JavaScript or a URL.
A Farmers administrator registers your application. Save the one-time API token securely on your server.
Call /whoami to confirm the actual authorized application and its public.read permission.
Read published Posts or Farms, with pagination. Optionally register a signed Post event receiver.
curl --fail-with-body -H "Authorization: Bearer $FARMERS_API_KEY" "https://chatfarm.bluepeople.co.za/wp-json/farmers-platform/v1/whoami"
Use an environment variable for FARMERS_API_KEY on your own trusted server. A successful response confirms the credential and permitted scope.
JSON over HTTPS. Maximum 25 items per page; no private conversations, support requests or Cloud membership data.
/healthPublic service identity
Public/whoamiAuthenticated application and scopes
Bearer/postsPublished Posts and Seed ideas
Bearer/farmsPublished business Farms
Bearercurl --fail-with-body -H "Authorization: Bearer $FARMERS_API_KEY" "https://chatfarm.bluepeople.co.za/wp-json/farmers-platform/v1/posts?per_page=10&page=1"
Receive post.published via registered HTTPS endpoint. The exact JSON body is HMAC-SHA256 signed with the one-time webhook secret.
Events are scheduled after a real published Post. They must not delay the member's posting action.
Validate X-Farmers-Signature over raw bytes. Reject invalid requests and deduplicate events.
Temporary failures (connection, 429 or 5xx) can be retried by WordPress Cron. A 2xx means receiver accepted delivery.
The first working method is secure REST + signed events. External OAuth and provider-specific adapters are separate certification work.
Public API consumption currently available; future commerce authorization separately
Provider OAuth, consent, mapping and callback certification pending
Provider APIs, policies and scopes must be reviewed
Publisher delivery and reporting contract pending
Verified payments remain separate from this public-data API
Scopes are restrictive by default. Keys can be revoked; no account impersonation or payment action is permitted through this release.
For production integrations, retain server-side secrets, use exact authorization callbacks and verify all provider signatures. The public document describes available contracts, not a universal no-setup adapter.