[Backend] -- Add Standardized “Retry-After” and “After” Semantics for Async Operations

[Devsol-01]

Description:
When endpoints return async semantics (e.g., 202 Accepted), clients need a consistent way to know when to poll again. Implement standardized response fields:

• retryAfterSeconds
• operationId
• statusEndpoint

Ensure these semantics are consistent across:

• exports
• background processing
• webhook-triggered jobs

Acceptance Criteria:

• Standard response schema implemented.
• At least 2 async endpoints migrated.
• Tests validate schema and values.

---

[Osifowora]

@Osifowora has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

​Hi maintainer, I would love to work on this issue. I can get started on it right away.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Osifowora to this issue.

[veemakama]

@veemakama has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi, i would love to work on this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @veemakama to this issue.

[Derry255]

@Derry255 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello Devsol-01, would love to take on this issue implement a good fix and submit a clean ready to merge PR..

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Derry255 to this issue.

[OpadijoIdris]

@OpadijoIdris has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Can i work on this please?

ℹ️ Repo Maintainers: To accept this application, review their application or assign @OpadijoIdris to this issue.

[goodness-cpu]

@goodness-cpu has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello Maintainer, I can fix this issue.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @goodness-cpu to this issue.

[Caneryy]

@Caneryy has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello, can I work on this issue?

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Caneryy to this issue.

[drips-wave]

Congratulations, @veemakama! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @veemakama: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been marked as completed by a Drips Wave moderator for @veemakama as part of the Stellar Wave Program's 6th Wave 🥳

Moderator's reason: [Auto-assessed] The contributor successfully implemented the standardized async response schema and migrated three endpoints (Data Export, Analytics Export, and Tax Reports), exceeding the requirement of two. Although PR #1128 was primarily titled for multi-tenancy, the code changes and documentation explicitly address issue #1125, and the PR has been merged by a maintainer.

😎 @veemakama: You earned 150 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

ℹ️ Note: This issue was marked complete via moderation. Points were issued even though the GitHub issue remains open.