Self Service

DELETE /merchant/{merchant_id}/admin/{admin_id}

Requires authentication with server or user access token.

Delete admin rights for user.

Help us improve

Did you spot an error? Or maybe you just have a suggestion for how we can improve? Leave us a comment.

Request

DELETE /api/2/merchant/{merchant_id}/admin/{admin_id}

merchant_id

required path parameter

Merchant ID

admin_id

required path parameter

Admin ID

Example request

cURL
curl https://login.schibsted.com/api/2/merchant/46000/admin/123123 -G \
   -X DELETE \
   -d "oauth_token=[access token]"
Java
SpidOAuthToken token = spidClient.getUserToken(code);
String responseJSON = spidClient.
    DELETE(token, "/merchant/46000/admin/123123").
    getResponseBody();

This example is an excerpt, see a full example

PHP
<?php
$client->auth();
echo var_dump($client->api("/merchant/46000/admin/123123", "DELETE"));

This example is an excerpt, see a full example

Clojure
(ns example
  (:require [spid-client-clojure.core :as spid]))

(let [client (spid/create-client "[client-id]" "[secret]")
      token (spid/create-user-token client "[code]")]
  (spid/DELETE client token "/merchant/46000/admin/123123"))

Response

This endpoint supports the JSON response format.

Success: 200 OK

Deletes an admin access to service

Admin

Admin object

_id

string

Admin ID

user_id

string

User ID

email

string

Email of admin

active

string

Admin active flag

ips

string

Allowed IPs for admin

merchants

string

Array of merchants for admin

services

string

Array of clients for admin

pages

string

Array of allowed pages for admin

time_limit

string

Last allowed time for admin

last_edited_by

string

User who last updated admin

created_by

string

User who created admin

updated

string

Time of last update

created

string

Time of creation

Failure cases

Some HTTP response codes are used for multiple error situations. There is no consistent way to tell these apart, but the error object will contain a textual explanation of the reason for the error. For explanation on OAuth related failures and errors see OAuth authentication failures.

  • 401 Unauthorized You don't have administration rights for this client.
  • 401 Unauthorized Your client doesn't have administration rights for this client.
  • 403 Forbidden Client is not authorized to access this API endpoint. Contact SPiD to request access.
  • 403 Forbidden Requesting IP is not whitelisted
  • 403 Forbidden Token does not have access to this merchant
  • 403 Forbidden Access token rejected
  • 404 Not Found Unknown client ID
  • 404 Not Found Client ID mismatch. The client making the request is no the owner of this resource, and does not have administrative privileges for it.
  • 420 Request Ratelimit exceeded

Comments/feedback

Do you have questions, or just want to contribute some newly gained insight? Want to share an example? Please leave a comment. SPiD reads and responds to every question. Additionally, your experience can help others using SPiD, and it can help us continuously improve our documentation.