Create a device token
post
/crmRestApi/resources/11.13.18.05/deviceTokens
Request
Header Parameters
-
Metadata-Context:
If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
-
REST-Framework-Version:
The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
-
Upsert-Mode:
Contains one of the following values: true or false. If true, the server performs an Upsert operation instead of a Create operation. During an Upsert operation, the server attempts to find an existing resource that matches the payload. If a match is found, the server updates the existing resource instead of creating a new one. If not found or false (default), the server performs a Create operation. Note that the Upsert operation isn't supported for date-effective REST resources.
Supported Media Types
- application/json
Root Schema : schema
Type:
Show Source
object
-
ApplicationName: string
Maximum Length:
50
The application name of the device token. -
DeviceToken: string
Maximum Length:
1000
The device token associated with a registered device. -
DeviceTokenTypeCd: string
Maximum Length:
30
The type of device that's being registered with the device token. -
PartyId: integer
(int64)
The party associated with device token.
-
PartyName: string
Maximum Length:
360
The party name associated with device token. -
UpsertMode: string
Indicates if the device token can be updated.
-
UserAgent: string
Maximum Length:
256
The user agent associated with the device. -
UserName: string
Maximum Length:
100
The user name associated with the device token.
Response
Supported Media Types
- application/json
Default Response
The following table describes the default response for this task.
Headers
-
Metadata-Context:
If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
-
REST-Framework-Version:
The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
Root Schema : deviceTokens-item-response
Type:
Show Source
object
-
ApplicationName: string
Maximum Length:
50
The application name of the device token. -
CreatedBy: string
Read Only:
true
Maximum Length:64
The user who created the device token. -
CreationDate: string
(date-time)
Read Only:
true
The date when the device token was created. -
DeviceToken: string
Maximum Length:
1000
The device token associated with a registered device. -
DeviceTokenId: integer
(int64)
Read Only:
true
The unique identifier of the device token. -
DeviceTokenTypeCd: string
Maximum Length:
30
The type of device that's being registered with the device token. -
LastUpdateDate: string
(date-time)
Read Only:
true
The date when the device token was last updated. -
LastUpdatedBy: string
Read Only:
true
Maximum Length:64
The user who last updated the device token. -
LastUpdateLogin: string
Read Only:
true
Maximum Length:32
The login details of the user who last updated the device token. -
links: array
Links
Title:
Links
The link relations associated with the resource instance. -
PartyId: integer
(int64)
The party associated with device token.
-
PartyName: string
Maximum Length:
360
The party name associated with device token. -
UpsertMode: string
Indicates if the device token can be updated.
-
UserAgent: string
Maximum Length:
256
The user agent associated with the device. -
UserGUID: string
Read Only:
true
Maximum Length:64
The user ID associated with the device token. -
UserName: string
Maximum Length:
100
The user name associated with the device token.
Nested Schema : Links
Type:
array
Title:
Links
The link relations associated with the resource instance.
Show Source
Nested Schema : link
Type:
Show Source
object
-
href: string
Title:
hyperlink reference
The URI to the related resource. -
kind: string
Title:
kind
Allowed Values:[ "collection", "item", "describe", "other" ]
The kind of the related resource. -
name: string
Title:
name
The name of the link to the related resource. -
properties: object
properties
-
rel: string
Title:
relation
Allowed Values:[ "self", "lov", "parent", "canonical", "child", "enclosure", "action", "custom" ]
The name of the relation to the resource instance. Example: self.
Nested Schema : properties
Type:
Show Source
object
-
changeIndicator: string
Change indicator or the ETag value of the resource instance.
Links
- DeviceToken_TypeCdLookup
-
Parameters:
- finder:
LookupTypeIsActiveEnabledFinder%3BBindLookupType%3DORA_SVC_NOTIFY_TOKEN_TYPE_CD
The following properties are defined on the LOV link relation:- Source Attribute: DeviceTokenTypeCd; Target Attribute: LookupCode
- Display Attribute: Meaning
- finder: