1
00:00:00,310 --> 00:00:02,430
If you build a job board, research tool

2
00:00:02,560 --> 00:00:04,670
or workforce dashboard, collecting

3
00:00:04,850 --> 00:00:06,560
records from different public portals

4
00:00:06,690 --> 00:00:08,490
can become a product of its own.

5
00:00:08,850 --> 00:00:10,640
LaborCurrent offers another starting

6
00:00:10,820 --> 00:00:13,470
point: structured workforce data through

7
00:00:13,520 --> 00:00:14,330
an API.

8
00:00:14,600 --> 00:00:16,210
In this walkthrough, we’ll look at how

9
00:00:16,260 --> 00:00:18,420
to choose a request, understand access

10
00:00:18,730 --> 00:00:20,930
limits, and keep a useful source trail

11
00:00:20,980 --> 00:00:22,750
inside the product you are building.

12
00:00:23,672 --> 00:00:25,282
Begin with one question your product

13
00:00:25,462 --> 00:00:26,422
needs to answer.

14
00:00:26,842 --> 00:00:29,362
For a regional workforce dashboard, that

15
00:00:29,452 --> 00:00:31,512
might be recent layoff notices in a

16
00:00:31,562 --> 00:00:32,662
selected state.

17
00:00:32,992 --> 00:00:34,702
The reference groups the endpoints by

18
00:00:34,752 --> 00:00:37,042
dataset, so you can start small before

19
00:00:37,262 --> 00:00:38,802
joining additional sources.

20
00:00:39,262 --> 00:00:41,902
Look for the fields and filters your

21
00:00:41,952 --> 00:00:43,772
workflow actually needs.

22
00:00:44,332 --> 00:00:46,892
This is employer-event data, not a list

23
00:00:46,982 --> 00:00:48,642
of individual candidates or their

24
00:00:48,692 --> 00:00:49,792
contact details.

25
00:00:50,786 --> 00:00:52,606
Here is the shape of a request.

26
00:00:52,986 --> 00:00:55,226
The API key belongs in the documented

27
00:00:55,406 --> 00:00:57,516
header, and the parameters narrow the

28
00:00:57,566 --> 00:00:58,976
data you ask for.

29
00:00:59,446 --> 00:01:01,286
Send your requests to laborcurrent dot

30
00:01:01,336 --> 00:01:04,166
com, using the endpoint shown in the API

31
00:01:04,206 --> 00:01:04,986
reference.

32
00:01:05,366 --> 00:01:07,966
Start with a small request, inspect the

33
00:01:08,016 --> 00:01:09,766
returned fields, and keep the source

34
00:01:09,906 --> 00:01:11,276
link with each record.

35
00:01:11,696 --> 00:01:13,716
Keep credentials out of screenshots,

36
00:01:13,896 --> 00:01:16,256
browser links and shared examples.

37
00:01:17,085 --> 00:01:18,815
Before wiring this into production,

38
00:01:19,105 --> 00:01:21,175
inspect a small response or the public

39
00:01:21,355 --> 00:01:22,025
sample.

40
00:01:22,335 --> 00:01:24,495
Check how the employer is named, how

41
00:01:24,545 --> 00:01:26,155
dates are represented, and how the

42
00:01:26,205 --> 00:01:27,485
source is carried through.

43
00:01:27,815 --> 00:01:29,835
Decide what your application will show

44
00:01:30,015 --> 00:01:31,855
when a field is missing or a query

45
00:01:32,035 --> 00:01:33,545
returns no matches.

46
00:01:33,925 --> 00:01:35,715
Keep the source reference with the

47
00:01:35,765 --> 00:01:38,015
record, so a user can move from your

48
00:01:38,055 --> 00:01:40,815
summary back to the evidence behind it.

49
00:01:41,774 --> 00:01:44,934
Next, match access to your use case.

50
00:01:45,304 --> 00:01:47,104
The pricing page separates request

51
00:01:47,194 --> 00:01:50,294
limits, history, freshness and export

52
00:01:50,384 --> 00:01:51,214
formats.

53
00:01:51,594 --> 00:01:53,884
A small evaluation and a production feed

54
00:01:53,974 --> 00:01:54,874
have different needs.

55
00:01:55,094 --> 00:01:57,564
If your interface is an AI tool, review

56
00:01:57,794 --> 00:01:59,334
the MCP guide too.

57
00:01:59,624 --> 00:02:01,914
MCP exposes data tools under the

58
00:02:02,004 --> 00:02:04,434
account’s access rules; it does not turn

59
00:02:04,474 --> 00:02:06,744
a limited key into unlimited access.

60
00:02:07,214 --> 00:02:08,784
Follow its current authentication

61
00:02:08,964 --> 00:02:10,944
instructions rather than assuming every

62
00:02:11,074 --> 00:02:12,954
client setting works the same way.

63
00:02:13,794 --> 00:02:15,904
For a first integration, keep the goal

64
00:02:15,994 --> 00:02:18,464
concrete: retrieve relevant records,

65
00:02:18,684 --> 00:02:20,844
show their dates and sources, and handle

66
00:02:21,024 --> 00:02:22,934
limits and empty results cleanly.

67
00:02:23,264 --> 00:02:25,294
Once that works, decide whether you need

68
00:02:25,384 --> 00:02:27,624
another dataset, exports or a

69
00:02:27,674 --> 00:02:28,934
higher-volume plan.

70
00:02:29,264 --> 00:02:31,554
Start at the documentation, review the

71
00:02:31,594 --> 00:02:33,714
current terms of the free account, and

72
00:02:33,754 --> 00:02:35,734
test the smallest workflow that would

73
00:02:35,824 --> 00:02:37,524
genuinely help your users.

74
00:02:38,024 --> 00:02:40,084
Build from evidence you can inspect.