Lunch Money Developer Portal
Lunch Money Developer Portal
Every new OAuth client starts in development, where only its owner can authorize it. This gives you time to build and test the application without making an unfinished integration available to other Lunch Money users.
When the application is ready, submit its client for review in the Developer Portal. A Lunch Money employee reviews the application information, requested permissions, redirect configuration, and other readiness requirements. Approval moves the client to active, allowing other Lunch Money users to authorize the application.
| State | What it means | Owner action |
|---|---|---|
development |
The client has not been submitted for review; only its owner can authorize it | Configure and test, then request review. |
pending_review |
Review has been requested and is waiting for or receiving review; review-critical fields are frozen | Continue owner testing or cancel the request. |
active |
The review was approved; other Lunch Money users may authorize the application | Operate within the approved identity and scope set. |
rejected |
Changes were requested | Read feedback, revise editable configuration, and resubmit. |
disabled |
Lunch Money disabled the client; its owner is notified, authorization is unavailable, and existing grants no longer work | Review the reason provided and contact developer support when appropriate. |
Deleted clients disappear from the owner's Developer Portal.
Submitting a client for review is how you make your application authorizable by Lunch Money users other than yourself. You can create and test a client with only basic information, but review requires a complete, user-facing application profile and production-ready configuration.
Before requesting review, provide:
Fully test the client before submission. A confidential web client also needs at least one active, non-expired secret; a native or public client does not.
Explain which features use each requested permission, how that access benefits users, and why narrower scopes are insufficient. If the client includes offline_access, explain why the integration must operate while the user is absent. You may also provide documentation, source-code, and demonstration URLs or context about changes made after earlier feedback.
A client may retain owner-only loopback callbacks alongside its production HTTPS callback, but a loopback-only client is not ready for review.
Submitting the request moves the client to pending_review and temporarily freezes review-critical fields. Reviews are usually completed within a couple of business days. You can continue developing and testing the application as the client owner while you wait. If you need to change a frozen field, cancel the request to return the client to development, make the change, and submit it again.
Lunch Money emails you when the review is complete. You can also check the current status and review history on the client's page in the Developer Portal.
If the review is denied, the Developer Portal shows feedback explaining what needs to change. Update the client's editable configuration and submit a new review request. Editing the client alone does not resubmit it or clear the rejected status.
There is no review comment thread, so use the new request's additional context to explain how you addressed the feedback. The Portal keeps the earlier request in the client's review history.
An active client can be authorized by other users. Reviewed identity fields, redirect configuration, and the registered scope set remain frozen after approval. Client-secret rotation and revocation remain available subject to lifecycle and security checks.
For an exceptional identity or configuration change, contact developer support. A scope change always requires a replacement client and user reauthorization.