Skip to content
Discussion options

You must be logged in to vote

Use your installation's origin, not bicho.fyi. Administrative reads require your admin bearer token; ingest credentials are only for collection. This example contains a placeholder, not a usable token:

curl --fail-with-body -sS -D - \
  -H 'Authorization: Bearer <admin-token>' \
  'https://your-bicho-worker.example/api/projects?limit=20'

Configure real credentials through your trusted secret-handling setup, without putting them in shared scripts or logs. The response lists project IDs, names, and hourly quotas, but no ingest credentials. Follow next_offset for additional projects.

Choose an ID returned by that request and read /api/:project_id/issues?status=all. Issue lists otherwise defa…

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by zapalblizh
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants