For up-to-date product documentation, see the IBM MobileFirst Foundation Developer Center.

Update GCM settings (PUT)

Uploads a GCM certificate to the application referenced by the application name.

Roles

Users in the following roles are authorized to perform this operation:

• mfpadmin
• mfpdeployer
• mfpoperator

Method

PUT

Path

/management-apis/2.0/runtimes/runtime-name/notifications/applications/application-name/gcmConf

Example

https://www.example.com/mfpadmin/management-apis/2.0/runtimes/myruntime/notifications/applications/myapplication/gcmConf?locale=de_DE

Path Parameters

runtime-name

The name of the runtime. This is the context root of the runtime web application, without the leading slash.

application-name

The name of the application.

Query Parameters

Query parameters are optional.

locale

The locale used for error messages.

Consumes

application/json, application/xml, text/xml

Produces

application/json, application/xml, text/xml

Payload

JSON Example

{
  "apiKey" : "AIzaSyBnWWReKAFrOPiw75QQAcRM",
  "senderId" : "11639055112",
}

XML Example

<?xml version="1.0" encoding="UTF-8"?>
<pushGCM
  apiKey="AIzaSyBnWWReKAFrOPiw75QQAcRM"
  senderId="11639055112"/>

Payload Properties

The payload has the following properties:

apiKey

GCM Api Key

senderId

The project ID that is signed up at Google API console

Errors

400

The request was not understood by the push server.

403

The user is not authorized to call this service.

404

The corresponding runtime or application is not found or not running.

415

Unsupported Media Type - The content type specified in Content-Type header is not application/json.

500

An internal error occurred.

Parent topic: REST API for the MobileFirst Server administration service