> For the complete documentation index, see [llms.txt](https://docs.faspay.co.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.faspay.co.id/getting-started/faspay-sendme/authentication/signature/relative-url.md).

# Relative URL

* Relative URL is the URL after the hostname & port number.
* Relative URL also includes the query string and must begin with a slash character, example :

<table><thead><tr><th width="367">Full URL</th><th>Relative URL</th></tr></thead><tbody><tr><td><a href="https://example.com/account/api/tokens">https://example.com/account/api/tokens</a></td><td> <strong>/account/api/tokens</strong></td></tr><tr><td><strong>https://example.com or https://example.com/</strong></td><td> <strong>/</strong></td></tr></tbody></table>

Relative URL must be URI-encoded according to the following rules:

* Do not URI-encode forward slash ( / ) if it was used as path component.
* Do not URI-encode question mark ( ? ), equals sign ( = ), and ampersand ( & ) if they were used as query string component: as separator between the path and query string, between query parameter and its value, and between each query parameter and value pairs.
* Do not URI-encode these characters: A-Z, a-z, 0-9, hyphen ( - ), underscore ( \_ ), period ( . ), and tilde ( \~ ) which are defined as unreserved characters in RFC 3986.
* Percent-encode all other characters not meeting the above conditions using the format: %XY, where X and Y are hexadecimal characters (0-9 and uppercase A-F). For example, the space character must be encoded as %20 (not using ’+’, as some encoding schemes do) and extended UTF-8 characters must be in the form %XY%ZA%BC.

The query string parameters must be re-ordered according to the following rules:

* Sorted by parameter name lexicographically
* If there are two or more parameters with the same name, sort them by parameter values.


---

# 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://docs.faspay.co.id/getting-started/faspay-sendme/authentication/signature/relative-url.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.