# Developer Resources

A host of tools and resources are readily available within the ORCA Developer Portal. Upon signing up, developers can explore the ORCA API to become familiar with the Platform and how data is accessed and manipulated.  

### **Browse API** 

Navigate to the Browse API tab to learn about the resources available to ORCA users, including Inbox, Calendar, and Patients and the methods used to access, modify, and submit data for each.

### **Documentation**

The Documentation tab contains valuable information regarding the API reference, authentication, and common errors that may occur following an API request. 

### **Change Log**

The Change Log tab displays the version history of the API and what has changed and/or improved, such as newly added permissions, security features, and endpoints.  

### **Security & Compliance**

This section explains the HIPAA requirements for developers to follow when creating Service Apps that have the ability to access a patient’s protected health information (PHI).

### **API Status**

Developers can check how the site is running at any time from the API tab to ensure Service Apps are running efficiently and take action if there is a delay in uptime. 

### **My Service Apps**

The My Service Apps tab is a hub for developers to create, test, submit, and manage their applications. Developers can view a list of their live Service Apps, request permissions, edit app content or media, and more.<br>


---

# Agent Instructions: 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:

```
GET https://dentalwhale.gitbook.io/documentation/developer-resources.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.