rusty_meta_threads 0.8.1

Community Rust SDK for integrating with Meta Threads API
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88

# rusty_meta_threads

![Crates.io Version](https://img.shields.io/crates/v/rusty_meta_threads)
[![Documentation](https://docs.rs/rusty_meta_threads/badge.svg)](https://docs.rs/rusty_meta_threads)
[![MIT/Apache-2 licensed](https://img.shields.io/crates/l/rusty_meta_threads)](./LICENSE-APACHE)

A community Rust SDK that helps interact with
[Meta Threads API](https://developers.facebook.com/docs/threads)

## Usage example

```
# configurations
# assuming these env values e.g. in `.env` file

THREADS_APP_ID=xxxxxxxxxxxxxxx
THREADS_APP_SECRET=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
THREADS_APP_AUTH_SCOPE=threads_basic
THREADS_AUTH_CODE_REDIRECT_URI=<REDIRECT_URL>
```

```rs
use rusty_meta_threads::{auth, profiles};

//------------------------------------------------------------
// CLIENT-SIDE

let login_url = auth::get_threads_login_url();
// now we can redirect the end-user to `login_url`,
// once the end-user logs in successfully, Threads will send
// a request to `<REDIRECT_URL>?code=<CODE>`, which we'll handle
// on the server-side

//------------------------------------------------------------
// SERVER-SIDE

// inside the HTTP endpoint handler logic for
// e.g. my-app.domain/auth
let code =
    auth::get_code_from_redirect_uri("<REDIRECT_URL_WITH_CODE>");

// `code` can now be exchanged for a short-lived bearer token
let short_lived_token =
    auth::get_short_lived_bearer_token(&code)
        .await
        .unwrap()
        .access_token;

// `short_lived_token` can be exchanged for
// a long-lived bearer token
let long_lived_token =
    auth::get_long_lived_bearer_token(&short_lived_token)
        .await
        .unwrap()
        .access_token;

// either `short_lived_token` or `long_lived_token` can be used
// to make API calls against Threads, for example:
let profile_info =
    profiles::get_profile_info(&long_lived_token)
        .await
        .unwrap();

// long-lived token can be refreshed
// as long as it doesn't expire yet
let refreshed_token =
    auth::refresh_long_lived_bearer_token(&long_lived_token)
        .await
        .unwrap()
        .access_token;
```

## Contributor notice

Please see [GOVERNANCE](./GOVERNANCE.md)

### Running tests

```bash
export ACCESS_TOKEN=replace_with_valid_threads_api_access_token
cargo test
# or if more details are needed
RUST_LOG=debug cargo test
```
Be aware: some tests may fail if `ACCESS_TOKEN` is expired, or
malformed. You may get a new token as per official
[Threads documentation](https://developers.facebook.com/docs/threads/get-started/get-access-tokens-and-permissions), and
then using their [Postman playground](https://www.postman.com/meta/threads/request/j8jvxf4/exchange-the-code-for-a-token).