Zig Requires Chilkat v11.0.0+

Xero 2 Legged OAuth for Private Application

This example demonstrates the REST object for 2-legged OAuth for a private application.

An application can setup OAuth1 for a given instance of the Chilkat REST object, and then use the instance for many REST API calls. This example demonstrates the OAuth1 setup and initial connection. This code would typically be placed in a subroutine/function to "initalize" the REST object before beginning to use it for REST HTTP requests.

Note: Xero private applications use 2 legged OAuth and bypass the user authorization workflow in the standard OAuth process. Private applications are linked to a single Xero organisation which is chosen when you register your application. In summary: 2-legged OAuth1 is for applications that access the data that they themselves own.

Zig

const std = @import("std");
const chilkat = @import("chilkat");

pub fn main(init: std.process.Init) !void {
    const alloc = init.arena.allocator();

    // This sample code would typically be placed in a subroutine or function
    // where the rest object is passed by reference.
    // It does the OAuth1 setup and makes the initial connection.
    const rest = try chilkat.Rest.init();
    defer rest.deinit();

    const consumer_key = "XERO_PRIVATE_APP_KEY";
    const consumer_secret = "XERO_PRIVATE_APP_SECRET";

    // Let's get our private key from our PFX (password protected), or the PEM (unprotected).
    // You can decide which to use.  Either is OK, although I would recommend keeping your
    // private keys in a PFX and not in an unprotected PEM.
    const pfx = try chilkat.Pfx.init();
    defer pfx.deinit();
    pfx.loadPfxFile("qa_data/certs/xero_private_app/public_privatekey.pfx", "PFX_PASSWORD") catch {
        std.debug.print("{s}\n", .{try pfx.getLastErrorText(alloc)});
        return;
    };

    const priv_key_from_pfx = try chilkat.PrivateKey.init();
    defer priv_key_from_pfx.deinit();
    pfx.privateKeyAt(0, priv_key_from_pfx) catch {
        std.debug.print("{s}\n", .{try pfx.getLastErrorText(alloc)});
        return;
    };

    // Or we can load from a PEM..
    const priv_key_from_pem = try chilkat.PrivateKey.init();
    defer priv_key_from_pem.deinit();
    priv_key_from_pem.loadPemFile("qa_data/certs/xero_private_app/privatekey.pem") catch {
        std.debug.print("{s}\n", .{try priv_key_from_pem.getLastErrorText(alloc)});
        return;
    };

    // Note: There are many other means for loading a private key, including
    // from other formats and directly from memory (i.e. not file-based).

    const oauth1 = try chilkat.OAuth1.init();
    defer oauth1.deinit();
    oauth1.setConsumerKey(consumer_key);
    oauth1.setConsumerSecret(consumer_secret);
    oauth1.setToken(consumer_key);
    oauth1.setTokenSecret(consumer_secret);
    oauth1.setSignatureMethod("RSA-SHA1");
    oauth1.setRsaKey(priv_key_from_pfx) catch {};

    // Make the initial connection.
    // A single REST object, once connected, can be used for many Xero REST API calls.
    // The auto-reconnect indicates that if the already-established HTTPS connection is closed,
    // then it will be automatically re-established as needed.
    const b_auto_reconnect = true;
    rest.connect("api.xero.com", 443, true, b_auto_reconnect) catch {
        std.debug.print("{s}\n", .{try rest.getLastErrorText(alloc)});
        return;
    };

    // Finally, install the OAuth1 authenticator.
    // (It make no difference whether this happens before or after the
    // connection is established.)
    rest.setAuthOAuth1(oauth1, false) catch {};

    std.debug.print("OK, the Xero OAuth1 is initialized and the REST object is ready to make REST API calls..\n", .{});
}