> For the complete documentation index, see [llms.txt](https://innowayit-1.gitbook.io/framework/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://innowayit-1.gitbook.io/framework/use-cases/api-strategy.md).

# API Strategy

> API stands for Application Programming Interface. The primary function of APIs is to enable applications to exchange data in a safe and secure way. Basically, an API is the point of contact between two applications. A real-life example would be a postman who delivers a letter from one person to another. 

> An API strategy highlights how APIs are going to be impleneted into an organisation. APIs have "become key facilitators of digital transformation — especially as organizations increasingly move data and applications to the cloud."

| Sponsor             | Scope           | Stakeholders                                                         |
| ------------------- | --------------- | -------------------------------------------------------------------- |
| Head of Digital/CIO | Enterprise-wide | <p>Internal and external developers<br>IT and business managers </p> |

#### Sponsors' Concerns

1. API as a product vs. API as a technical integration&#x20;
2. Inside-out vs. Outside-in perspectives&#x20;
3. API monetisation&#x20;
4. Public, private, and partners API consumers&#x20;
5. API platform selection&#x20;

### FORMULATION

<details>

<summary>PLAN</summary>

</details>

<details>

<summary>ENGAGE</summary>

</details>

<details>

<summary>DIAGNOSE</summary>

</details>

<details>

<summary>DECIDE</summary>

</details>

<details>

<summary>GUIDE</summary>

</details>

<details>

<summary>DEFINE OKR</summary>

</details>

### EXECUTION

<details>

<summary>ACT</summary>

</details>

<details>

<summary>REPORT</summary>

</details>

<details>

<summary>RETROSPECT</summary>

</details>


---

# 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://innowayit-1.gitbook.io/framework/use-cases/api-strategy.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.