Posting a Question to the Community

In the developer community you can ask other developers and the operations team about the API and integration implementations. Posts are reviewed by the operations team before they go public; once approved, they appear in the community list.

Before you post

• Make sure you're logged in with your developer account
• Use keyword search to check whether the same question has already been posted
• Don't include secrets such as API keys or access tokens in the body (they are grounds for rejection)

How to post

• Open the community top page
• Click the "Post a question" button at the top right
• Fill in the following
  • Title: a phrase that makes the content clear at a glance (e.g. "invalid signature on Webhook signature verification")
  • Category: choose from Authentication / API / General / Announcements
  • Body: be specific about the symptom, what you tried, the error message, and the behavior you expect
• Click "Post"

Flow after posting

• Right after posting, it shows "Will be published after administrator approval" (other developers can't see it yet)
• An approval request is automatically sent to the operations team
• Approval or rejection is usually decided within one business day
• The result is sent to your registered email address

If approved

You'll receive an email titled "[Approved] Your question has been published." The question appears in the community top page and is now open to receive answers from other developers.

If rejected

You'll receive an email titled "[Notice] Your post could not be published," with the reason for rejection in the body. You can revise it based on the reason and re-post. Common rejection reasons are as follows.

• Contains secrets (API keys, tokens, personal information, etc.)
• Content unrelated to ReceiptRoller
• Advertising a commercial service
• The content is unclear, making it hard to answer

Tips for asking questions

• Make the title specific: not "I'm getting an error" but "POST /api/v1/receipts returns 400"
• Include the full error message: pasting it as text rather than a screenshot lets others reach it via search
• Number your reproduction steps: in the form 1. … 2. … 3. …
• Write what you've already tried: e.g. "Confirmed XX in the docs," "Verified on version YY"
• Mask secrets: keep only the first few characters, like "Authorization: Bearer eyJhbGc..."

Related articles

• Receiving answers to your questions