Resources API

Submit a community resource

Anyone with a developer key can propose a new resource. Submissions enter a review queue and go live only after a Bynli moderator approves them.

Endpoint

POSTbynli.com

POST https://bynli.com/dash/api/resources/submit
Authorization: Bearer bapi_pk_…
Content-Type: application/json

Request body

Field	Type	Required	Notes
`name`	string	Yes	Display name, under 200 characters.
`description`	string	No	One or two sentences on what it does.
`category`	string	No	One of the category slugs. If omitted, it's inferred from your text.
`address`	string	No	Single-line street address.
`phone`	string	No	Contact phone.
`website`	string	No	Public URL.
`hours`	string	No	Free-text hours.
`team_id`	integer	No	Optional hint for which organization's directory you think this belongs to. A moderator makes the final call.

Example

curlbynli.com

curl -X POST https://bynli.com/dash/api/resources/submit \
  -H "Authorization: Bearer bapi_pk_…" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Neighborhood Free Fridge",
    "description": "24/7 community fridge at 5th & Main",
    "category": "food",
    "address": "500 Main St",
    "website": "https://example.org"
  }'

Response

202 Acceptedapplication/json

{
  "success": true,
  "id": 312,
  "status": "pending",
  "message": "Submission received. A Bynli moderator will review it before it goes live."
}

Be a good neighbor. Duplicate, spammy, or unrelated submissions are rejected. Repeated low-quality submissions from the same key may slow down or block further reviews from that key.

Errors

Status	When
`401`	Missing or invalid bearer token.
`403`	Your key doesn't have the submission scope.
`422`	`name` is missing or too long.
`429`	You've submitted a lot recently — slow down and retry later.

What happens after you submit

A Bynli moderator reviews your submission.
If approved, the resource goes live in the organization's directory.
If rejected, it's marked as such and won't be shown.