# DID Repository DID Repository is the core of DID routing. It defines all the routing plan for each DID. Each record in DID repository defines how each DID is to be routes: * From which DID vendor the DID is to be originated from * What DID billing rule will be charged by the DID vendor for this DID * To which DID client the DID is to be terminated to * What DID billing rule should be charged to the DID client for this DID The Switch Admin can add each DID routing record one by one via the user interface under DID > DID repository. Alternatively, Switch Admin can also use Import to upload multiple DIDs at the same time. It is also possible that a DID is brought from DID vendor but it is not yet assigned to any DID client. Those DIDs that are not assigned to any DID client is considered unassigned DIDs. An unassigned DID can be searched and purchased by DID client via Client portal or Client API. If you don't want any DID to be searchable, you can turn on the "reserved" flag, then the DID will not be searchable by user via the client portal. --- # 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://cookbook.denovolab.com/quick-setup-for-origination-traffic/did-repository.md?ask= ``` 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.