> For the complete documentation index, see [llms.txt](https://help.adalo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.adalo.com/publishing-apps/publishing-to-the-apple-app-store/setup-annual-payment-for-your-apple-developer-account.md).

# Setup Annual Payment for your Apple Developer Account

{% hint style="info" %}
**\*\*\* Apple requires that you pay them $99/year to have a developer account**

1. Once your Apple Developer Account has been approved, you can click the link from the email to login (or go here: <https://developer.apple.com/account>)
2. Agree to the terms of service
3. Enter your payment information for the $99 per year fee (also, select the option to make the fee automatically recur each year)
   1. Note that this payment will take 48 hours to process
      {% endhint %}

## Help

If you need additional help with this article, you can always ask in our [community forum](https://forum.adalo.com/)! Be sure to paste the link to this article in your post as well!


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.adalo.com/publishing-apps/publishing-to-the-apple-app-store/setup-annual-payment-for-your-apple-developer-account.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.