You have no favorites... yet!
Use the Library tree on the left to select a Choreo to call from your gateway device.
Use the Library tree on the left to select a Choreo to call from your edge device via the gateway.
Library . Xively . APIKeys . UpdateKey
Updates an existing APIKey.
/*
TembooTask class placeholder
*/
/*
TembooTask header placeholder
*/
Since you've changed your device configuration, you'll need to tell us about this new device.
This feature is in experimental mode - pricing coming soon.
Send your code straight to a GitHub repository.
Your code will be visible by others in your repos. Keep credentials private by saving a Profile or commit code with Placeholder inputs.
The following files will be added to this repo:
You'll be able to edit and share your code from TI's CCS Cloud IDE.
The following will be sent to CCS Cloud:
/*
Your auto-generated code will appear here once you've configured your device above.
*/
/*
A header file containing your Temboo account information will appear here once you've
configured your device above.
*/
/*
Please log in to generate proxy server code for use with the JavaScript SDK.
*/
This Choreo updates a specified API Key.
If the APIKey you would like to update does not have sufficient permissions, please specify a MasterAPIKey with full permissions to modify that APIKey.
The optional inputs allows you to update the specified API Key with the most common options. You can include custom (and multiple) permissions by using the CustomPermissions input. For advanced configuration options you can create your own custom key in the CustomKey input variable as a xml or json string (you can specify which format in the CustomType variable - default is JSON).
The documentation for this Xively resource can be found here.
Here's an example list of acceptable inputs:
APIKey: {THE XIVELY API KEY YOU WOULD LIKE TO UPDATE}
AccessMethods: put,post
Label: Key Label
The following is an example of a valid CustomKey in JSON:
{ "key":{ "label":"sample key", "private_access": true, "permissions":[ { "access_methods":["put"], "source_ip": "128.44.98.129", "resources": [ { "feed_id": 123456 } ] }, { "access_methods": ["get", "put"], "source_ip": "123.456.789.012" } ] } }
The following is an example of a valid CustomPermissions input in JSON:
"permissions":[ { "access_methods":[ "get" ] }, { "access_methods":[ "put" ], "referer":"my-domain.com", "source_ip":"128.44.98.129", "resources":[ { "feed_id":123199 } ] } ]
The following is an example of a valid CustomPermissions input in XML:
<permissions> <permission> <access-methods> <access-method>get</access-method> </access-methods> </permission> <permission> <referer>my-domain.com</referer> <source-ip>128.44.98.129</source-ip> <access-methods> <access-method>put</access-method> </access-methods> <resources> <resource> <feed-id>123199</feed-id> </resource> </resources> </permission> </permissions>
For a successful key update, the ResponseStatusCode variable should return 200.
https://ACCOUNT_NAME.temboolive.com/callback/google
© 2025 Temboo, Inc Privacy Terms