> For the complete documentation index, see [llms.txt](https://docs.didforsale.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didforsale.com/voice-and-sms-apis/voice-and-sms/didml-reference-doc/voice-api-request-params.md). # Voice API Request Params ## DIDforSale sends Request to your webserver As soon as someone dials your DIDforSale phone number, DIDforSale will send an HTTP request to the weburl you have configured with the phone number. *How do I know which URL is being connected with a specific phone phone number?*\ Log in to your DIDforSale account, click on a phone number and see which URL its linked with. You can direct each phone number to connect with unique URL’s if you have specific instructions/purpose for them. *What is the importance of URL connected with the phone number?*\ This URL holds the instruction file defined by you. So for a phone number to be handled in a specific order, there has to be a URL that its linked to. This URL holds the dial plan or the instruction file that’s created by you. When someone dials your DIDforSale phone number, an HTTP **request** is send to the connected URL, The system then will wait to get response from the \ and handle the call respectively. ![Data flow between DFS platform and Client Application](/files/-LVdh5yvo443qhjiOaK1) ### What is included in the Request? Idea is to give you flexibility to built a dynamic application. So when we send first request for the URL, we also pass some information about the call in the post variables. ***POST:*** DIDforSale will submit the call related information in a form to the URL when request is made You can use all or some of them. To=”..DIALED\_NUMBER..”\&From=”..caller\_id\_number..”\&CallerName=”..caller\_id\_name..”\&callSid=”..UUID..”\&Direction=”..direction..”\&CallStatus=”..callstatus **To:** The number that end user dialed.\ **From:** Callers Caller ID\ **CallerName:** Name of the caller from database, If name is not registered, then we can provide City and State (*\*Extra charges may apply*)\ **callSid:** Unique id for each call. Can be useful for reporting purpose.\ **Direction:** Whether the call is an inbound or outbound call.\ **Callstatus:** What state the call is in at the time of this request. (*On hold, in Queue, answered etc.)* --- # 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.didforsale.com/voice-and-sms-apis/voice-and-sms/didml-reference-doc/voice-api-request-params.md?ask=&goal= ``` `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.