@@ -346,7 +346,9 @@ def create_entry(
346
346
per_unit_cost_basis, as the calculation of the invoice total is done on that
347
347
basis.
348
348
349
- metadata: User-specified key/value pairs for the resource.
349
+ metadata: User-specified key/value pairs for the resource. Individual keys can be removed
350
+ by setting the value to `null`, and the entire metadata mapping can be cleared
351
+ by setting `metadata` to `null`.
350
352
351
353
per_unit_cost_basis: Can only be specified when entry_type=increment. How much, in USD, a customer
352
354
paid for a single credit in this block
@@ -499,7 +501,9 @@ def create_entry(
499
501
For example, this can be used to note an increment refers to trial credits, or
500
502
for noting corrections as a result of an incident, etc.
501
503
502
- metadata: User-specified key/value pairs for the resource.
504
+ metadata: User-specified key/value pairs for the resource. Individual keys can be removed
505
+ by setting the value to `null`, and the entire metadata mapping can be cleared
506
+ by setting `metadata` to `null`.
503
507
504
508
extra_headers: Send extra headers
505
509
@@ -662,7 +666,9 @@ def create_entry(
662
666
For example, this can be used to note an increment refers to trial credits, or
663
667
for noting corrections as a result of an incident, etc.
664
668
665
- metadata: User-specified key/value pairs for the resource.
669
+ metadata: User-specified key/value pairs for the resource. Individual keys can be removed
670
+ by setting the value to `null`, and the entire metadata mapping can be cleared
671
+ by setting `metadata` to `null`.
666
672
667
673
extra_headers: Send extra headers
668
674
@@ -816,7 +822,9 @@ def create_entry(
816
822
For example, this can be used to note an increment refers to trial credits, or
817
823
for noting corrections as a result of an incident, etc.
818
824
819
- metadata: User-specified key/value pairs for the resource.
825
+ metadata: User-specified key/value pairs for the resource. Individual keys can be removed
826
+ by setting the value to `null`, and the entire metadata mapping can be cleared
827
+ by setting `metadata` to `null`.
820
828
821
829
void_reason: Can only be specified when `entry_type=void`. The reason for the void.
822
830
@@ -971,7 +979,9 @@ def create_entry(
971
979
For example, this can be used to note an increment refers to trial credits, or
972
980
for noting corrections as a result of an incident, etc.
973
981
974
- metadata: User-specified key/value pairs for the resource.
982
+ metadata: User-specified key/value pairs for the resource. Individual keys can be removed
983
+ by setting the value to `null`, and the entire metadata mapping can be cleared
984
+ by setting `metadata` to `null`.
975
985
976
986
extra_headers: Send extra headers
977
987
@@ -1207,7 +1217,9 @@ def create_entry_by_external_id(
1207
1217
per_unit_cost_basis, as the calculation of the invoice total is done on that
1208
1218
basis.
1209
1219
1210
- metadata: User-specified key/value pairs for the resource.
1220
+ metadata: User-specified key/value pairs for the resource. Individual keys can be removed
1221
+ by setting the value to `null`, and the entire metadata mapping can be cleared
1222
+ by setting `metadata` to `null`.
1211
1223
1212
1224
per_unit_cost_basis: Can only be specified when entry_type=increment. How much, in USD, a customer
1213
1225
paid for a single credit in this block
@@ -1360,7 +1372,9 @@ def create_entry_by_external_id(
1360
1372
For example, this can be used to note an increment refers to trial credits, or
1361
1373
for noting corrections as a result of an incident, etc.
1362
1374
1363
- metadata: User-specified key/value pairs for the resource.
1375
+ metadata: User-specified key/value pairs for the resource. Individual keys can be removed
1376
+ by setting the value to `null`, and the entire metadata mapping can be cleared
1377
+ by setting `metadata` to `null`.
1364
1378
1365
1379
extra_headers: Send extra headers
1366
1380
@@ -1523,7 +1537,9 @@ def create_entry_by_external_id(
1523
1537
For example, this can be used to note an increment refers to trial credits, or
1524
1538
for noting corrections as a result of an incident, etc.
1525
1539
1526
- metadata: User-specified key/value pairs for the resource.
1540
+ metadata: User-specified key/value pairs for the resource. Individual keys can be removed
1541
+ by setting the value to `null`, and the entire metadata mapping can be cleared
1542
+ by setting `metadata` to `null`.
1527
1543
1528
1544
extra_headers: Send extra headers
1529
1545
@@ -1677,7 +1693,9 @@ def create_entry_by_external_id(
1677
1693
For example, this can be used to note an increment refers to trial credits, or
1678
1694
for noting corrections as a result of an incident, etc.
1679
1695
1680
- metadata: User-specified key/value pairs for the resource.
1696
+ metadata: User-specified key/value pairs for the resource. Individual keys can be removed
1697
+ by setting the value to `null`, and the entire metadata mapping can be cleared
1698
+ by setting `metadata` to `null`.
1681
1699
1682
1700
void_reason: Can only be specified when `entry_type=void`. The reason for the void.
1683
1701
@@ -1832,7 +1850,9 @@ def create_entry_by_external_id(
1832
1850
For example, this can be used to note an increment refers to trial credits, or
1833
1851
for noting corrections as a result of an incident, etc.
1834
1852
1835
- metadata: User-specified key/value pairs for the resource.
1853
+ metadata: User-specified key/value pairs for the resource. Individual keys can be removed
1854
+ by setting the value to `null`, and the entire metadata mapping can be cleared
1855
+ by setting `metadata` to `null`.
1836
1856
1837
1857
extra_headers: Send extra headers
1838
1858
@@ -2390,7 +2410,9 @@ async def create_entry(
2390
2410
per_unit_cost_basis, as the calculation of the invoice total is done on that
2391
2411
basis.
2392
2412
2393
- metadata: User-specified key/value pairs for the resource.
2413
+ metadata: User-specified key/value pairs for the resource. Individual keys can be removed
2414
+ by setting the value to `null`, and the entire metadata mapping can be cleared
2415
+ by setting `metadata` to `null`.
2394
2416
2395
2417
per_unit_cost_basis: Can only be specified when entry_type=increment. How much, in USD, a customer
2396
2418
paid for a single credit in this block
@@ -2543,7 +2565,9 @@ async def create_entry(
2543
2565
For example, this can be used to note an increment refers to trial credits, or
2544
2566
for noting corrections as a result of an incident, etc.
2545
2567
2546
- metadata: User-specified key/value pairs for the resource.
2568
+ metadata: User-specified key/value pairs for the resource. Individual keys can be removed
2569
+ by setting the value to `null`, and the entire metadata mapping can be cleared
2570
+ by setting `metadata` to `null`.
2547
2571
2548
2572
extra_headers: Send extra headers
2549
2573
@@ -2706,7 +2730,9 @@ async def create_entry(
2706
2730
For example, this can be used to note an increment refers to trial credits, or
2707
2731
for noting corrections as a result of an incident, etc.
2708
2732
2709
- metadata: User-specified key/value pairs for the resource.
2733
+ metadata: User-specified key/value pairs for the resource. Individual keys can be removed
2734
+ by setting the value to `null`, and the entire metadata mapping can be cleared
2735
+ by setting `metadata` to `null`.
2710
2736
2711
2737
extra_headers: Send extra headers
2712
2738
@@ -2860,7 +2886,9 @@ async def create_entry(
2860
2886
For example, this can be used to note an increment refers to trial credits, or
2861
2887
for noting corrections as a result of an incident, etc.
2862
2888
2863
- metadata: User-specified key/value pairs for the resource.
2889
+ metadata: User-specified key/value pairs for the resource. Individual keys can be removed
2890
+ by setting the value to `null`, and the entire metadata mapping can be cleared
2891
+ by setting `metadata` to `null`.
2864
2892
2865
2893
void_reason: Can only be specified when `entry_type=void`. The reason for the void.
2866
2894
@@ -3015,7 +3043,9 @@ async def create_entry(
3015
3043
For example, this can be used to note an increment refers to trial credits, or
3016
3044
for noting corrections as a result of an incident, etc.
3017
3045
3018
- metadata: User-specified key/value pairs for the resource.
3046
+ metadata: User-specified key/value pairs for the resource. Individual keys can be removed
3047
+ by setting the value to `null`, and the entire metadata mapping can be cleared
3048
+ by setting `metadata` to `null`.
3019
3049
3020
3050
extra_headers: Send extra headers
3021
3051
@@ -3251,7 +3281,9 @@ async def create_entry_by_external_id(
3251
3281
per_unit_cost_basis, as the calculation of the invoice total is done on that
3252
3282
basis.
3253
3283
3254
- metadata: User-specified key/value pairs for the resource.
3284
+ metadata: User-specified key/value pairs for the resource. Individual keys can be removed
3285
+ by setting the value to `null`, and the entire metadata mapping can be cleared
3286
+ by setting `metadata` to `null`.
3255
3287
3256
3288
per_unit_cost_basis: Can only be specified when entry_type=increment. How much, in USD, a customer
3257
3289
paid for a single credit in this block
@@ -3404,7 +3436,9 @@ async def create_entry_by_external_id(
3404
3436
For example, this can be used to note an increment refers to trial credits, or
3405
3437
for noting corrections as a result of an incident, etc.
3406
3438
3407
- metadata: User-specified key/value pairs for the resource.
3439
+ metadata: User-specified key/value pairs for the resource. Individual keys can be removed
3440
+ by setting the value to `null`, and the entire metadata mapping can be cleared
3441
+ by setting `metadata` to `null`.
3408
3442
3409
3443
extra_headers: Send extra headers
3410
3444
@@ -3567,7 +3601,9 @@ async def create_entry_by_external_id(
3567
3601
For example, this can be used to note an increment refers to trial credits, or
3568
3602
for noting corrections as a result of an incident, etc.
3569
3603
3570
- metadata: User-specified key/value pairs for the resource.
3604
+ metadata: User-specified key/value pairs for the resource. Individual keys can be removed
3605
+ by setting the value to `null`, and the entire metadata mapping can be cleared
3606
+ by setting `metadata` to `null`.
3571
3607
3572
3608
extra_headers: Send extra headers
3573
3609
@@ -3721,7 +3757,9 @@ async def create_entry_by_external_id(
3721
3757
For example, this can be used to note an increment refers to trial credits, or
3722
3758
for noting corrections as a result of an incident, etc.
3723
3759
3724
- metadata: User-specified key/value pairs for the resource.
3760
+ metadata: User-specified key/value pairs for the resource. Individual keys can be removed
3761
+ by setting the value to `null`, and the entire metadata mapping can be cleared
3762
+ by setting `metadata` to `null`.
3725
3763
3726
3764
void_reason: Can only be specified when `entry_type=void`. The reason for the void.
3727
3765
@@ -3876,7 +3914,9 @@ async def create_entry_by_external_id(
3876
3914
For example, this can be used to note an increment refers to trial credits, or
3877
3915
for noting corrections as a result of an incident, etc.
3878
3916
3879
- metadata: User-specified key/value pairs for the resource.
3917
+ metadata: User-specified key/value pairs for the resource. Individual keys can be removed
3918
+ by setting the value to `null`, and the entire metadata mapping can be cleared
3919
+ by setting `metadata` to `null`.
3880
3920
3881
3921
extra_headers: Send extra headers
3882
3922
0 commit comments