Keys

Before Creating a Key

This event trigger is fired when an key object is created in the Mashery platform.  Keys are created:

    During the registration process (via the portal)
    Via the Administrative Dashboard (Keys tab)
    Via the Mashery API.

This event trigger event is executed before the actual key object is saved in the Mashery database.  As such, data can be enriched, e.g. adding data from your own systems into the Mashery key object, or a decision could be returned to not permit the save operation.

Event Trigger Call Structure (Mashery to Customer-hosted Endpoint)

Example Call:

POST /v1/key?event=pre-create&txn=46f6497a6b284411aa715427608e6df2 HTTP/1.1      
Host: api.customer.com 
Accept: application/json
Key-Agent: Mashery Event Trigger 1.0
Content-Type: application/json
{
    "member": {
        "region": "",
        "external_id": "",
        "phone": "",
        "address1": "",
        "address2": "",
        "area_status": "active",
        "registration_ipaddr": "",
        "blog": "http://blog.mashery.com",
        "im": "",
        "country_code": "",
        "uri": "http://www.mashery.com",
        "object_type": "member",
        "first_name": "Event Trigger",
        "display_name": "event triggerTester",
        "username": "event triggerTester",
        "created": "2012-10-09T15:34:50Z",
        "updated": "2012-10-09T17:54:40Z",
        "email": "jpollock@mashery.com",
        "postal_code": "",
        "company": "Mashery",
        "last_name": "Test",
        "locality": "",
        "imsvc": ""
    },
    "oauth_rate_limit_ceiling": 0,
    "limits": [
        {
            "source": "service",
            "ceiling": 2,
            "period": "second"
        },
        {
            "source": "service",
            "ceiling": 5000,
            "period": "day"
        }
    ],
    "oauth_qps_limit_exempt": false,
    "application": {
        "preferred_protocol": "",
        "tags": "",
        "external_id": "",
        "status": "draft",
        "ads_system": "",
        "type": "",
        "uri": "http://www.mashery.com",
        "object_type": "application",
        "id": 146082,
        "username": "event triggerTester",
        "preferred_output": "",
        "how_did_you_hear": "",
        "created": "2012-10-09T17:54:41Z",
        "updated": "2012-10-09T17:58:21Z",
        "description": "This is a great application",
        "usage_model": "",
        "name": "Test App for event triggerTester",
        "ads": false,
        "notes": "",
        "commercial": false
    },
    "oauth_user_limits": [],
    "status": "active",
    "group_id": 0,
    "oauth_qps_limit_ceiling": 0,
    "qps_limit_ceiling": 0,
    "qps_limit_exempt": false,
    "apikey": "mkz884zzebkmufs3r2ebwspn",
    "object_type": "key",
    "username": "event triggerTester",
    "protected_methods": false,
    "oauth_rate_limit_exempt": false,
    "service_key": "nrm4mmu843n2q2rd22fzj49c",
    "created": "2012-10-09T17:58:43Z",
    "updated": "2012-10-09T17:58:43Z",
    "rate_limit_ceiling": 0,
    "rate_limit_exempt": false,
    "service": {
        "service_key": "nrm4mmu843n2q2rd22fzj49c",
        "updated": "2012-08-23T20:04:16Z",
        "created": "2011-11-05T01:47:29Z",
        "name": "Catalog API",
        "limits": [
            {
                "source": "service",
                "ceiling": 2,
                "period": "second"
            },
            {
                "source": "service",
                "ceiling": 5000,
                "period": "day"
            }
        ],
    },
    "secret": "wMkKYJr",
    "required_referer": ""
}

Expected Response Sent from Customer-hosted Endpoint

HTTP/1.1 200 OK
Server: nginx/1.3.13
Date: Fri, 05 Apr 2013 18:41:41 GMT
Content-Type: application/json
Connection: keep-alive
Vary: Accept-Encoding
X-Original-Transfer-Encoding: chunked
Content-Length: 18

{"type":"proceed"}

HTTP/1.1 200 OK
Server: nginx/1.3.13
Date: Fri, 05 Apr 2013 18:43:13 GMT
Content-Type: application/json
Connection: keep-alive
Vary: Accept-Encoding
X-Original-Transfer-Encoding: chunked
Content-Length: 77

{"type":"proceed_with_changes","params": [{"apikey": "12124mycustomkey"}]}

HTTP/1.1 400 Bad Request
Server: nginx/1.3.13
Date: Fri, 05 Apr 2013 18:43:57 GMT
Content-Type: application/json
Connection: keep-alive
Vary: Accept-Encoding
X-Original-Transfer-Encoding: chunked
Content-Length: 136

{"type":"stop","error": {"code":-32600, "message":"That will never work","data":[{"field":"apikey","message":"Key is not unique in our system"}]}}

Any other responses will be considered failure and save operation will not be performed. Additionally, if the execution of the event trigger takes longer than 10 seconds, then a timeout will occur, and the save operation will not be performed.

Before Updating a Key

This event trigger is fired when an key object is updated, or modified, in the Mashery platform.  Keys are updated:

    By the user in the Portal My Account area
    Via the Administrative Dashboard (Keys tab)
    Via the Mashery API.

This event trigger event is executed before the actual key object is saved in the Mashery database.  As such, data can be enriched, e.g. adding data from your own systems into the Mashery key object, or a decision could be returned to not permit the save operation.

Event Trigger Call Structure (Mashery to Customer-hosted Endpoint)

Example Call:

PUT /v1/key/14398445?event=pre-update&txn=8807190f73701b1bdf5a2272f445366f HTTP/1.1      
Host: api.customer.com 
Accept: application/json
Key-Agent: Mashery Event Trigger 1.0
Content-Type: application/json
{
    "member": {
        "region": "",
        "external_id": "",
        "phone": "",
        "address1": "",
        "address2": "",
        "area_status": "active",
        "registration_ipaddr": "",
        "blog": "http://blog.mashery.com",
        "im": "",
        "country_code": "",
        "uri": "http://www.mashery.com",
        "object_type": "member",
        "first_name": "Event Trigger",
        "display_name": "event triggerTester",
        "username": "event triggerTester",
        "created": "2012-10-09T15:34:50Z",
        "updated": "2012-10-09T17:54:40Z",
        "email": "jpollock@mashery.com",
        "postal_code": "",
        "company": "Mashery",
        "last_name": "Test",
        "locality": "",
        "imsvc": ""
    },
    "oauth_rate_limit_ceiling": 0,
    "limits": [
        {
            "source": "service",
            "ceiling": 2,
            "period": "second"
        },
        {
            "source": "service",
            "ceiling": 500000,
            "period": "day"
        }
    ],
    "oauth_qps_limit_exempt": false,
    "application": {
        "preferred_protocol": "",
        "tags": "",
        "external_id": "",
        "status": "draft",
        "ads_system": "",
        "type": "",
        "uri": "http://www.mashery.com",
        "object_type": "application",
        "id": 146082,
        "username": "event triggerTester",
        "preferred_output": "",
        "how_did_you_hear": "",
        "created": "2012-10-09T17:54:41Z",
        "updated": "2012-10-09T17:58:21Z",
        "description": "This is a great application",
        "usage_model": "",
        "name": "Test App for event triggerTester",
        "ads": false,
        "notes": "",
        "commercial": false
    },
    "oauth_user_limits": [],
    "status": "active",
    "group_id": 0,
    "oauth_qps_limit_ceiling": 0,
    "qps_limit_ceiling": 0,
    "qps_limit_exempt": false,
    "apikey": "mkz884zzebkmufs3r2ebwspn",
    "object_type": "key",
    "username": "event triggerTester",
    "protected_methods": false,
    "oauth_rate_limit_exempt": false,
    "service_key": "nrm4mmu843n2q2rd22fzj49c",
    "created": "2012-10-09T17:58:43Z",
    "updated": "2012-10-09T17:58:43Z",
    "rate_limit_ceiling": 0,
    "rate_limit_exempt": false,
    "service": {
        "service_key": "nrm4mmu843n2q2rd22fzj49c",
        "updated": "2012-08-23T20:04:16Z",
        "created": "2011-11-05T01:47:29Z",
        "name": "Catalog API",
        "limits": [
            {
                "source": "service",
                "ceiling": 2,
                "period": "second"
            },
            {
                "source": "service",
                "ceiling": 5000,
                "period": "day"
            }
        ],
    },
    "secret": "wMkKYJr",
    "required_referer": ""
}

Expected Response Sent from Customer-hosted Endpoint

HTTP/1.1 200 OK
Server: nginx/1.3.13
Date: Fri, 05 Apr 2013 18:41:41 GMT
Content-Type: application/json
Connection: keep-alive
Vary: Accept-Encoding
X-Original-Transfer-Encoding: chunked
Content-Length: 18

{"type":"proceed"}

HTTP/1.1 200 OK
Server: nginx/1.3.13
Date: Fri, 05 Apr 2013 18:43:13 GMT
Content-Type: application/json
Connection: keep-alive
Vary: Accept-Encoding
X-Original-Transfer-Encoding: chunked
Content-Length: 77

{"type":"proceed_with_changes","params": [{"status": "waiting"}]}

HTTP/1.1 400 Bad Request
Server: nginx/1.3.13
Date: Fri, 05 Apr 2013 18:43:57 GMT
Content-Type: application/json
Connection: keep-alive
Vary: Accept-Encoding
X-Original-Transfer-Encoding: chunked
Content-Length: 136

{"type":"stop","error": {"code":-32600, "message":"That will never work","data":[{"field":"apikey","message":"Key is not unique in our system"}]}}

Any other responses will be considered failure and save operation will not be performed. Additionally, if the execution of the event trigger takes longer than 10 seconds, then a timeout will occur, and the save operation will not be performed.

Before Deleting a Key

This event trigger is fired when an key object is deleted in the Mashery platform.  Keys can be deleted:

    By the user in the My Account area of the Portal
    Via the Administrative Dashboard (Keys tab)
    Via the Mashery API.

This event trigger event is executed before the actual key object is deleted  in the Mashery database.

There are special considerations for deleting key objects, please understand them before calling this method.  When a key object is deleted, the username associated with that member is not released.  Therefore, any subsequence member.create for that same username will fail with a duplicate object error.

Event Trigger Call Structure (Mashery to Customer-hosted Endpoint)

Example Call:

DELETE /v1/key/14398445?event=pre-delete&txn=07e108fd854ae11e66b5abdf7d83585f HTTP/1.1      
Host: api.customer.com 

Expected Response Sent from Customer-hosted Endpoint

HTTP/1.1 200 OK
Server: nginx/1.3.13
Date: Fri, 05 Apr 2013 18:41:41 GMT
Content-Type: application/json
Connection: keep-alive
Vary: Accept-Encoding
X-Original-Transfer-Encoding: chunked
Content-Length: 18

{"type":"proceed"}

HTTP/1.1 400 Bad Request
Server: nginx/1.3.13
Date: Fri, 05 Apr 2013 18:43:57 GMT
Content-Type: application/json
Connection: keep-alive
Vary: Accept-Encoding
X-Original-Transfer-Encoding: chunked
Content-Length: 136

{"type":"stop","error": {"code":-32600, "message":"That will never work"}}

Any other responses will be considered failure and save operation will not be performed. Additionally, if the execution of the event trigger takes longer than 10 seconds, then a timeout will occur, and the save operation will not be performed.