---
sourceDocument: Australia API Reference
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/api-reference

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia API Reference

ft:clusterId :

    - crapiref

bundleId :

    - crapiref

workflow :

    - Creator


---

# Define a request header

# Define scripted REST API headersa scripted REST API request header {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

Define scripted REST API request headers to control which headers the API accepts and can respond with.

## Vorbereitungen

There must be a scripted REST API defined before you can create request headers.

Role required: web_service_admin

## Prozedur

1. Navigate to AllSystem Web ServicesScripted REST APIs.
2. Select a scripted REST API record.
3. In the Request Headers related list, select New.
4. Enter a Header name.
5. Enter a Short description and Example value to explain how to use the header.
6. Select Submit.
7. **Wahlweise:** From the Request Headers tab, locate the header name and set Is required to "true" to document this request header as required.  
   Hinweis:  
   If you set Is required to "true", the scripted REST service doesn't enforce requiring the header. To enforce requiring a header, you must add logic to the scripted REST API resource that rejects requests that are missing the required headers.
{#t_DefineRESTServiceHeaders__steps_dxp_5b4_bs}

## Nächste Maßnahme

After defining available headers, associate the headers with a scripted REST resource. For more information, see [Associate a request header with a resource](https://servicenow-prod.fluidtopics.net/zdG9T3plo0Q~YdfXkeFHow "Define which request headers are expected for each resource within a scripted REST API.").